IP Console applications allow an attendant to monitor the Busy Lamp Field (BLF) status of extensions from the Busy Lamp Field panel.
The Busy Lamp Field panel displays the following states for each monitored extension:
Busy Lamp Field status:
Idle: extension is idle
Ringing: line or extension is ringing
Busy: line or extension is busy
Idle/Do Not Disturb: extension is idle and has Do Not Disturb enabled
Ringing/Do Not Disturb Ringing: extension is ringing and has Do Not Disturb enabled
Busy/Do Not Disturb: extension is busy and has Do Not Disturb enabled
Not Monitored: extension is no longer programmed in MiVoice Business as a BLF entry
Status Not Displayed: Busy Lamp Field feature has been turned off. All BLF entries in the Busy Lamp Field panel of the console will display a blank icon or "Status Not Displayed"
Extension Number (Directory Number)
Name
Department
Location
This feature applies to IP Console applications only.
You can configure Busy Lamp Field monitors against directory numbers associated with single-line sets, multiline sets, and all types of Broadcast Groups.
A directory number can be monitored by a busy lamp group consisting of up to 64 monitoring devices. Consoles are not counted as one of the 64 monitoring devices in a busy lamp group.
The console provides limited DSS functionality. The attendant can only place a call to a monitored extension by pressing the associated DSS key on the console.
A Busy Lamp Field (BLF) list can be unique to a console or it can be shared across multiple consoles.
This feature is supported across Portable Directory Number (clustered) networks. Remote BLF keys that are programmed on the host controller of the IP Console application can be displayed in the console's Busy Lamp Field panel. See DSS/BLF key programming for instructions on how to program BLF keys to function across a cluster.
If a console is monitoring a remote device across the network and the device changes state, there can be a short delay, typically 1 to 2 seconds, before the state of the device is updated in the console BLF panel.
This feature is not supported in a resilient system. If a resilient IP Console application fails over to its secondary controller, the BLF list functionality is disabled.
If a monitored device is resilient and on a controller that is remote to the IP Console application's controller, the device will lose communication with IP console when the device fails over to its secondary controller. While the monitored device is on the secondary controller, the IP console BLF list is not updated with the BLF status of the remote device. After the device re-homes to its primary, the console will not begin receiving status updates from the device until you enter the "BLF REFRESH CEID ALL" maintenance command or the set user makes or receives a call.
You can program a Multicall line appearance of an extension on multiple phones (see Line Types and Appearances). The Busy Lamp Field indicators for each of these Multicall line appearances will appear idle unless all appearances of that extension are busy or in DND state. In the BLF panel of the IP Console application, the BLF indicator for an extension will also be displayed as idle unless all appearances of the extension are busy or in DND state.
IP Console applications support as many BLFs as there are BLF Groups provisioned in the Dimension Selection form on the host MiVoice Business platform.
To set up this feature, you must complete programming in both MiVoice Business and the IP Console application. The main steps are
In the MiVoice Business System Administration Tool, program BLF appearances for the extensions that the attendants want to monitor.
Install IP Console application software on each PC that requires the BLF feature.
Configure the extensions into the Busy Lamp Field panels of the consoles.
Obtain a list of the extensions that need to be monitored.
If the required remote DSS/BLF keys are not already programmed in the system, program a personal IP phone for the attendant and then assign DSS/BLF keys against a "virtual" PKM. A "virtual" PKM is only programmed in the system and doesn't physically exist. To program a personal IP phone (5020 IP or 5220 IP) for the attendant, see Program Multiline IP Telephones.
Next, program a "virtual" PKM against the attendant's prime extension number:
Go to the Multiline IP Sets form.
Select the extension number of the attendant's personal IP phone.
Click Change.
Set the PKM field to " PKM 12", " PKM 48", or "Dual PKM".
Click Save.
NOTE: You can program the virtual PKM against any IP phone extension in the system that is capable of supporting PKMs (5020 IP or 5220 IP Phones). However, it is easier to keep track of the virtual PKM if you program it against an IP phone that has been assigned to the attendant.
In the Multiline Set Keys form assign the monitored extensions to the keys on a virtual PKM.
Go to the Multiline IP Sets form.
Search and locate the prime directory number of the attendant's personal IP phone.
Click Change All Members.
Scroll down to the first available virtual PKM key. For example, if the attendant is assigned a 5020 IP device type (which has 14 programmable keys) the first virtual PKM key is key 15.
Starting at the first virtual PKM key, set the Line Type to " DSS/Busy Lamp", leave the URL field blank, enter the directory number of the monitored extension, and set the Ring Type to "No Ring".
NOTE: You do not need to complete the Button Label field. Although you can enter a label in this field, it will not be displayed on the IP Console application interface.
Complete the key programming for each extension that requires monitoring.
Click Save.
MiVoice Business Console.
Refer to the IP Console application Help for instructions.